Yeh - horses for course, many ways to do it. Was just offering a suggestion.    It still has to be anchored to the line above - been like this since inception and no improvement to the way it works. ... View more

Anchored objects can't be on the same line.    Fix would be to anchor it in the line above - if there is one.  You could thread a mini frame above your existing one - and set the text anchor to go in that frame, then position the anchored object.   But unfortunately that's the limitation of an anchored object, text wrap doesn't work properly unless it's anchored to the line above. ... View more

What's moot? You haven't provided a tangible file to see what's going on - I can only guess.  ... View more

Again, need to see samples of what you're doing, what's working and what's not.  ... View more

That is a nice workaround - but can become problematic if the leading changes, or the text shifts to the top/bottom of the column, the anchored object can sometimes run off the page.    A more stable solution if it's just beside a paragraph is using a table - it flows with the text and the image won't suddenly drop off. It's a bit of an extra step but not much - and it's the most reliable way I have found.  ... View more

Did you try the EPUB route to see if it produces a different result? That export usually generates a more complete stylesheet, so it can be a good way to check whether InDesign is dropping definitions during the standard HTML export or if something else is at play.   I’ve honestly no idea either it’s really hard to know what’s happening without seeing a sample file, the resulting HTML/CSS, or even a simplified test version that reproduces the issue. InDesign’s export logic can be pretty opaque, and sometimes small document quirks (like local overrides, nested styles, or features it doesn’t fully support) can cause whole chunks of CSS to disappear.   What’s your end goal with this? Are you trying to get fully usable HTML/CSS directly out of InDesign for web use, or just a structural export to hand off to developers? The approach might differ depending on that, if you need a clean, ready-to-use front-end output, you may have better luck with in5 or a custom script, since they translate InDesign’s styles far more faithfully than Adobe’s native exporter.   If you can share a minimal example, it’d help narrow down whether this is a bug, a limitation, or something in the export setup. ... View more

Hmm sorry about that - I don't know either let me go a bit deeper see if it makes sense. Well I'm no an epub/or HTML/CSS exporting guy - very rarely do it, so I'm trying to help and maybe some of what I say will point you in a direction. Lets understand this a bit more   Styles that visibly change appearance aren’t showing up in idGeneratedStyles.css - is this part right?   Does this make sense to you InDesign will only output CSS for styles it recognises as authored paragraph/character/object styles or explicit exported overrides. If formatting is applied as a local override, as part of a nested object, or via features InDesign doesn’t translate to CSS on export, you’ll see class names in the HTML but no matching rules in the generated CSS.... ----> Is this what you're seeing?   If so Confirm they’re real styles, not local overrides. Select the text and open the Paragraph/Character Styles panel. If it shows “+” or “Override” next to the style name, click the menu Clear Overrides (or Redefine Style if you want the override baked into the style). Re-export and check idGeneratedStyles.css.   Verify the style actually contains CSS-exportable attributes. Some features (anchored objects, certain glyph/typographic features, nested bullets, anchored images) don’t always become CSS properties. Try adding a simple, clearly exportable change (e.g., font-size or color) to one style and re-export to see if it appears.   Check Export Tagging vs Exported CSS settings. Export Tagging assigns class names (structural). Export preferences control whether CSS definitions are written. In the HTML export dialog, ensure “Generate CSS” / “Include Style Definitions” are checked and that “Preserve Local Overrides” is OFF if you want clean style rules.   Look for ParaOverride-* origin. Those come from local formatting that wasn’t saved into the style. Clearing/redefining the style or removing overrides will remove ParaOverride-* and let InDesign output the canonical style rule.   Try an EPUB export as a test. Export to EPUB (Fixed or Reflowable) and inspect the CSS inside the EPUB package (OEBPS/Styles). EPUB export often produces more complete CSS rules and can help pinpoint what’s being lost in the HTML export path. Minimal test file.   Create a tiny test doc: one paragraph style, apply it to text, give it a single property (font-size or color), export HTML. If the rule appears, incrementally add the real formatting from your production doc until something drops it  that reveals the problematic attribute.   If none of the above explains it You might need to drop a sample indesign file to see what's going on. ... View more

I thnk that's how InDesign’s HTML export is working as designed it only outputs CSS for styles that actually change appearance. The “Export Tagging” classes you set are structural, not stylistic, so InDesign just names them in the HTML without generating matching CSS. If you need full style definitions, add real formatting to each style,  maybe try the EPUB, or switch to a plugin like in5, Mag+ or PubCoder for more control. ... View more

All I can do is ask.  ... View more

You’re right it’s a limitation, especially for multilingual users or anyone switching UI languages for collaboration or training.   Unfortunately, InDesign treats each language as a separate installation environment, which is why all user data (workspaces, shortcuts, preferences, etc.) gets stored in folders like: ~/Library/Preferences/Adobe InDesign/Version <xx>/<locale> (macOS) or %AppData%\Adobe\InDesign\Version <xx>\<locale> (Windows).   That means switching from cs_CZ to en_US doesn’t delete your presets - they’re just in the Czech folder. You can manually copy them across by duplicating the corresponding subfolders (for example, “Workspaces,” “Keyboard Shortcuts,” and “Print Presets”) from the Czech folder into the English one.   Quick steps: Close InDesign.   Go to your old locale folder (e.g. cs_CZ). Copy the folders for your custom items (like Workspaces, InDesign Shortcut Sets, PDF Presets, etc.). Paste them into the new locale folder (en_US).   Relaunch InDesign.   It’s definitely something Adobe could handle more gracefully  a migration or shared profile option would make a huge difference.   You might also want to file it as a feature request on the Adobe InDesign UserVoice page it helps when feedback like this gets visibility from other professionals. https://indesign.uservoice.com/forums/601021-adobe-indesign-feature-requests     ... View more

Thanks for following up, that explains it, the special documents were part of the filename and not added by the system.  ... View more

I made some modifications to this script a while ago - it wasn't working exactly for me at the time the way I needed - I can't recall what was wrong or what I changed but I did something.   /** * Release All Anchored Objects. * (Tested in InDesign 18.3 on MacOS) */ function main() { var doc = app.activeDocument, items = doc.allPageItems, counter = 0, oversetCounter = 0; for (var i = items.length - 1; i >= 0; i--) { // Check if the object's parent is a character and it has anchored object settings if ( items[i].parent.constructor.name === 'Character' && items[i].hasOwnProperty('anchoredObjectSettings') ) { // Only proceed if the anchored object is inside a text frame (i.e. not in overset text) if (items[i].parent.parentTextFrames.length > 0) { // Force the object into an anchored state items[i].anchoredObjectSettings.anchoredPosition = AnchorPosition.ANCHORED; // Release the anchored object items[i].anchoredObjectSettings.releaseAnchoredObject(); counter++; } else { oversetCounter++; } } } alert('Released ' + counter + ' anchored objects.' + (oversetCounter > 0 ? ' Skipped ' + oversetCounter + ' overset objects.' : '')); } app.doScript(main, ScriptLanguage.JAVASCRIPT, undefined, UndoModes.ENTIRE_SCRIPT, 'Release All Anchored Objects'); ... View more

Ah I see I didn’t fully get that you might not have realised the consequences of the choices made when creating the document.   When you set up a new file in InDesign, there’s an option for Facing Pages (used for books, magazines, or any layout that opens like a spread (same way a magazine or book opens) and Non-Facing Pages (used for single sheets, posters, or digital outputs).   If you choose Facing Pages, InDesign automatically arranges the pages in spreads so page 1 will be on the right-hand side by itself, and pages 2–3 will appear together as a left and right pair. That affects how the page order looks in the Pages panel and how content lines up across the spine.   If you use Non-Facing Pages, every page is treated as an individual canvas there’s no left/right pairing, which can be easier for single-page documents or exports.   I'll explain it from start to begining on how to spot what is happening for the future.   This is what you've shown us on your original screenshot  We can tell it's on a Parent Page - as on the bottom it shows B-Parent So your screenshot looks like this - as the Parent Pages are not showing - that was the first clue, you are showing Parent Pages A and the pages and there's no artwork on the right hand side - which tells me there's a hidden parent page - and the biggest clue in your screenshot is it shows B-Parent at the bottom.   - when you scroll in the parent page area to find the pages you designed on.  Now - when we put the Parent Pages into the Pages area - it shows correctly     Delete the first blank page and you get what you got   This is one way to fix it - without having to do too much correction. Right click and Untick this option   Then drag 1 down beside 2   ---------------------------------------------------------------------- In future consider if you need Facing Pages or Non-Facing pages before you start. Remember Facing Pages is typically only required for documents like books/magazines/leaflets/newsletters etc.    Everything else, like posters, or simple 1 page - only require to have 1 page - and at the size you require.    Hope that helps.             ... View more

Looks like you've put it on the Parent Pages, I can see 2 pages in the Parent Page area and only 1 page in the pages area.    You need to drag your Parent Pages into the Pages area - and delete the blank page. ... View more

Sounds like a licensing sync issue on Adobe’s end rather than anything local. Since you’ve already tried another device, it’s likely your account entitlement isn’t being recognised properly.   Try signing out of all devices via your Adobe account page, then log back in fresh on one device.   If that doesn’t help, clear the Creative Cloud cache Clear Creative Cloud cache: Windows: C:\Users\<yourname>\AppData\Local\Adobe\OOBE   rename the folder to OOBE_old . macOS: ~/Library/Application Support/Adobe/OOBE   rename to OOBE_old . Then relaunch Creative Cloud and sign in again.   or reinstall the CC desktop app using Adobe’s Cleaner Tool. Creative Cloud Cleaner Tool https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html   If others are seeing this too, it might be a temporary server issue. You could always hit the Free Trial and work on that until the issue is resolved - I think it gives you 7 days full access - and this should be enough time to resolve. ... View more

This is happening because your laptop uses a Snapdragon (ARM-based) processor. At the moment, Adobe hasn’t released ARM-compatible versions of all Creative Cloud apps, InDesign, Dreamweaver, and Audition are among those not yet supported.   Photoshop and a few others run fine because they already have native ARM builds or work under emulation, but InDesign simply isn’t available on Windows ARM yet. Adobe has said they’re working on wider support, but there’s no confirmed release date.   If you need InDesign right now, the only reliable option is to use a computer with an Intel or AMD processor. Or try the InDesign Beta - it seems to be listed in the link below - so it's probably coming very soon.   https://helpx.adobe.com/ie/download-install/apps/system-requirements/apps-compatibility-copilot.html   ... View more

Typically if I want text and images with captions to flow with the text, I'll put them in a table within the text.    So a 2 row 1 column table.  In top row put the image In the bottom row put the caption (or anchor the generated caption if that's what you're doing?)   Not it's in the table, the table flows with the text.  Just in the Table Options set them to Keep With Next Row - https://helpx.adobe.com/indesign/using/formatting-tables.html#:~:text=To%20keep%20the%20selected%20rows%20together%2C%20select%20Keep%20With%20Next%20Row.   Then you can resize your image without having scale the text - no need for them to be grouped.    Once you do one image/caption table you can reuse them in other places.      ... View more

Did you try the creative cloud cleaner tool - I have a saved snippet here to post   Reinstalling rarely fixes everything - you can do a complete reinstall using the Creative Cloud Cleaner Tool https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html ... View more

If @Mike Witherell compendium of fixes is not working or still have issues   I did see this the other day, could be similar https://community.adobe.com/t5/indesign-discussions/indesign-v21-not-starting-after-update-win-11/m-p/15570413#M640032     ... View more

Feature requests need to be submitted here for best traction https://indesign.uservoice.com/forums/601021-adobe-indesign-feature-requests   Thanks for posting this - I'm sure others need it. ... View more

I'll have to think about it some more.    Had different head hurt day with different problem today than yesterday. Time for the weekend anyway - thanks for the help and tips. ... View more

It's not the filetype that's the problem. it's text wrap is applied to something on the page.  You double click into a graphic to move it around - when you double click does the text wrap show? As you can have independent text wrap on a frame and also on a graphic within the frame.    The fact that you deleted the red background says that it's a text wrap either on that frame or the graphic within the frame.    As others have said - if you select your text frame and go to text frame options and choose Ignore Text Wrap does the issue go away? It definitely loos like text wrap.  ... View more

My apologies if I wasn't clear. I don't need to make a layer or move items onto a layer - although it's not a bad idea...  Many thanks for helping out with the script it is giving me some ideas to try.    I just want to check that there's a text frame on that layer on each page - parent page or not.  The text frame either has to have the Text Variable or the text equal to the file name.    If it's on the Parent Page it's fine don't need an alert ----------------------->unless it's not a text variable or the text in it doesn't match the file name.  If it's on Page 1 - same criteria as above --------->and subsequent pages.   But I think I can try something with this.  The layer move is a good idea, sometimes the Code is not on the right layer. This makes sense to check that it's on the right layer and move it if it's not. ... View more

It's kinda working - it reads the text frame and says it has the variable data in it - but when I remove the text and input garbage text it says it's still variable data I still can't work out the logic to only flag an alert if it's not an all pages so it's fine if it's on the parent page and that it shows on all pages  But would need to know if it's not on all pages (if absent from parent page), or if the text is manually typed in (not variable data).  Practically, it should just flag if the Code layer is missing text frame containing either a text variable or text that matches the filename.    But I'm not sure it can read the text on pages where it's applied via the parent page. Probably way overthinking it. My head hurts. #targetengine "textVariableCheckEngine" code (function() { var TECH_LAYER_REGEX = /technical|codes|code/i; // --- Normalize string for comparison --- function normalizeSafe(input) { try { return String(input).replace(/[^a-z0-9]/gi, "").toLowerCase().trim(); } catch (e) { return ""; } } // --- Safely extract variable text only if it exists --- function extractVariableText(tvi) { if (!tvi) return ""; try { if (tvi.resultText && tvi.resultText.contents) { var text = String(tvi.resultText.contents); if (normalizeSafe(text).length > 0) return text; } } catch(e){} return ""; } // --- Get all text from a frame: contents + valid text variables --- function getFrameText(frame) { var txt = ""; try { if (frame.contents) txt += frame.contents; } catch(e){} try { if (frame.textVariableInstances && frame.textVariableInstances.length > 0) { for (var i=0;i<frame.textVariableInstances.length;i++){ txt += extractVariableText(frame.textVariableInstances[i]); } } } catch(e){} return normalizeSafe(txt); } // --- No open document --- if (app.documents.length === 0) { alert("No open document"); return; } var doc = app.activeDocument; var fileToken = normalizeSafe(doc.name.replace(/\.[^\.]+$/, "")); var masterHasToken = {}; // --- Check parent/master spreads --- for (var m=0; m<doc.masterSpreads.length; m++){ var master = doc.masterSpreads[m]; var frames = []; try { frames = master.pageItems.everyItem().getElements(); } catch(e){} var found = false; for (var f=0; f<frames.length; f++){ var frame = frames[f]; try { if (frame.constructor.name !== "TextFrame") continue; if (!frame.itemLayer || !TECH_LAYER_REGEX.test(frame.itemLayer.name)) continue; var text = normalizeSafe(frame.contents); var variableText = getFrameText(frame); if (text.indexOf(fileToken) !== -1 || variableText.indexOf(fileToken) !== -1){ found = true; break; } } catch(e){ continue; } } masterHasToken[master.name] = found; } // --- Check document pages --- var missingPages = []; for (var p=0; p<doc.pages.length; p++){ var page = doc.pages[p]; var pageFound = false; // 1) Check if applied master already contains token try { if (page.appliedMaster && page.appliedMaster.isValid){ if (masterHasToken[page.appliedMaster.name]) pageFound = true; } } catch(e){} // 2) Check frames on the page if (!pageFound){ var frames = []; try { frames = page.pageItems.everyItem().getElements(); } catch(e){} for (var f=0; f<frames.length; f++){ var frame = frames[f]; try { if (frame.constructor.name !== "TextFrame") continue; if (!frame.itemLayer || !TECH_LAYER_REGEX.test(frame.itemLayer.name)) continue; var text = normalizeSafe(frame.contents); var variableText = getFrameText(frame); if (text.indexOf(fileToken) !== -1 || variableText.indexOf(fileToken) !== -1){ pageFound = true; break; } } catch(e){ continue; } } } if (!pageFound) missingPages.push(page.name); } // --- Output --- var masterWarning = ""; var anyMasterHas = false; for (var key in masterHasToken) { if (masterHasToken.hasOwnProperty(key) && masterHasToken[key]) { anyMasterHas = true; break; } } if (!anyMasterHas) masterWarning = "WARNING: No parent/master spread contains filename/variable on Technical layer.\n\n"; if (missingPages.length === 0) { alert(masterWarning + "All pages contain filename/variable on Technical layer.\nFilename: " + doc.name); } else { alert(masterWarning + "⚠ Filename/variable missing on Technical layer for pages:\n" + missingPages.join(", ") + "\nExpected: " + doc.name); } })(); ... View more

This is as far as I got with the code - when i got into trouble I tried flushing it through ChatGPT and Gemini - but neither could resolve the issue or figure out why it's not working.  This is literally where I have left off.  #targetengine "textVariableCheckEngine" (function () { var enableEventListener = false; // Set true later if you want automatic check on save if (enableEventListener) { var handlerAlreadyAdded = true; for (var i = 0; i < app.eventListeners.length; i++) { if (app.eventListeners[i].name === "textVariableCheckHandler") { handlerAlreadyAdded = true; break; } } if (!handlerAlreadyAdded) { var el = app.addEventListener("beforeSave", textVariableCheck, false); el.name = "textVariableCheckHandler"; } } textVariableCheck(); // Run immediately for manual test function textVariableCheck() { try { if (app.documents.length === 0) return; var doc = app.activeDocument; var usedVariables = []; // --- Scan pages and master spreads --- function scanContainer(container) { for (var p = 0; p < container.length; p++) { var page = container[p]; var pageItems = page.allPageItems; for (var i = 0; i < pageItems.length; i++) { var item = pageItems[i]; if (item.hasOwnProperty("textVariableInstances")) { var instances = item.textVariableInstances; for (var j = 0; j < instances.length; j++) { var v = instances[j]; if (v && v.associatedTextVariable && v.associatedTextVariable.name != null) { var nameStr = String(v.associatedTextVariable.name); // Classic loop duplicate check var alreadyAdded = false; for (var k = 0; k < usedVariables.length; k++) { if (usedVariables[k] === nameStr) { alreadyAdded = true; break; } } if (!alreadyAdded) usedVariables.push(nameStr); } } } } } } scanContainer(doc.pages); scanContainer(doc.masterSpreads); if (usedVariables.length === 0) { alert("⚠ No text variables found in pages or master pages."); } // --- Code Layer check --- var fileName = doc.name.replace(/\.[^\.]+$/, ""); var techMismatch = false; var techFound = false; for (var t = 0; t < doc.textFrames.length; t++) { var tf = doc.textFrames[t]; if (tf.itemLayer && /Code/i.test(tf.itemLayer.name)) { techFound = true; // Ignore frames that have text variables if (tf.textVariableInstances.length > 0) continue; // Clean content for comparison var content = String(tf.contents) .replace(/[\s\u00A0\u200B-\u200D\uFEFF]/g, "") .replace(/[^\x20-\x7E]/g, "") .toLowerCase(); var cleanFile = String(fileName) .replace(/[\s\u00A0\u200B-\u200D\uFEFF]/g, "") .replace(/[^\x20-\x7E]/g, "") .toLowerCase(); if (content.indexOf(cleanFile) === -1) { techMismatch = true; break; } } } if (!techFound) { alert("⚠ No text found on the Code layer."); } else if (techMismatch) { alert("⚠ Code layer text does NOT match the filename: " + fileName); } // Silent if all is okay } catch (e) { alert("Error in textVariableCheck: " + e); } } })();   ... View more

Sure    1. Trying to check the parent page for a text variable or text that matches the filename 2. Trying to check the page 1 for a variable, or for text matches the filename 3. When on page 1 and not page 2 (or vice versa) it doesn't recognise as it finds it on one of the pages Something like the attached.  For example, the text variable isn't always on the parent page. But it picks up the filename.  So I'm trying to catch on all pages where the code is not the filename either by text or by text variable.  ... View more

Part Meaning Example Match \d+ One or more digits ( 0–9 ) Matches 5 , 21 , 103 \K "Keep out" marker — it resets the start of the match, so anything before \K is not included in the final match. If the text is 5th , the regex sees 5th but only reports th . th The literal letters t and h Matches th \b Word boundary — ensures th ends at a boundary (like space, punctuation, or end of word). So 5th matches, but 5thrones does not.   https://www.oreilly.com/library/view/grep-pocket-reference/9780596157005   https://creativepro.com/files/kahrel/indesign/grep_classes.htm     ... View more

Ok wonder if it's the extra bleed on the right hand side.      ... View more

Looks like the ski is outside the page area and in the safety zone.  Images have to reach the bleed area. And the ski doesn't.    I'd say that's it. ... View more